If you add a new component (such as SAS^® OpRisk Monitor) to an existing configuration of the third maintenance release for SAS 9.2 (TS2M3), you must stop all Oracle WebLogic servers before any configuration with the SAS^® Deployment Wizard. If you do not stop the servers, the configuration fails.

Prior to SAS 9.2 TS2M3, this action was not necessary. The configuration only added new servers in a multiple-server configuration. It did not update any existing servers.

Starting with SAS 9.2 TS2M3, the configuration updates your domain configuration so that it makes recommended server command-line changes. It also addresses other configuration attributes that should change. Any changes that are made are reported in the generated file Instructions.html. The servers must be stopped for this procedure. If you are working with a federated (multiple-machine) middle tier, you only need to stop the servers on the machine where you are adding the new products.

This SAS 9.2 TS2M3 requirement does have a problem that affects multiple-server, single-machine configurations. The Java Node Manager and Oracle AdminServer are launched during the WebLogic configuration step. The managed server on which the new application will reside is automatically started before the application deploys. If this application depends on other SAS applications that are not on the same server, the new application might not deploy if it must connect to the other SAS applications at initialization time. It is common for SAS applications to require the SAS Web Infrastructure Platform Services and Themes applications to be running when they initialize. To avoid this problem, start the first managed server manually after the SAS Deployment Wizard completes the WebLogic configuration step. There is usually sufficient time to do this while the new application is building, but it does require the person performing the configuration to monitor the process.

Operating System and Release Information